Arrow keys / Click to navigate

Cloud Operations on AWS

Module 4: Deploy and Update Resources

Cloud Operations on AWS

Module Overview

CloudOps in deployment
Developing a tagging strategy
Using AMIs for deployment
AWS Control Tower for multi-account deployment

CloudOps Deployment Requirements

Repeatable: templates, AMIs, infrastructure as code
Trackable: tags, ownership, costs, organization
Monitored: performance, auditing, compliance, logs, metrics
Compliant: standardization and company policy

Introduction to Tags

Metadata assigned to resources for managing, searching, and filtering
Example: example-corp:cost-center = 78214
Tags are case-sensitive — use lowercase and hyphens
AWS predefined tags vs. customer-defined tags

Tools to Automate Resource Tagging

AWS CloudFormation — apply tags on creation
AWS Service Catalog — AutoTags and TagOptions
IAM policy condition keys to enforce tags
AWS Organizations tag policies

AMIs for Deployment

Components: instance volume template, launch permissions, block device mappings
Sources: AWS, user-built, AWS user community, AWS Marketplace
aws ec2 create-image --instance-id ... --name ...
Copy AMIs across Regions with aws ec2 copy-image

EC2 Image Builder

Streamlines building, testing, and distributing AMIs
Automate lifecycle policies for image versions
Integrates with Lambda and Step Functions

AWS Control Tower Controls

Type	Behavior	Implementation
Preventive	Disallows actions	Service control policies
Detective	Detects noncompliance	AWS Config
Proactive	Scans before provisioning	CloudFormation hooks

Troubleshooting Scenario

Issue: User data fails to run — e.g., httpd startup specified but not running on the instance.

Solution: Log in to the instance, verify the user data, and check /var/log/cloud-init-output.log.

Module Summary

Next: Module 5 — Automate Resource Deployment

Module 4 Mind Map

Click branch to expand

1 / 10